Transparency as a Requirement

نویسندگان

  • Mahmood Hosseini
  • Alimohammad Shahri
  • Keith Phalp
  • Raian Ali
چکیده

The concept of transparency refers to the possibility of accessing information, intentions or behaviours that are revealed through a process of disclosure [4]. It is usually linked to accountability, openness, and e ciency [1]. Transparency depends on the accessibility and availability of information and how this can support users in the process of decision making [4]. In requirements engineering literature, socio-technical systems (STSs) are typically seen as a set of inter-dependent social and technical actors, as is the case with goal modelling and business process modelling. Amongst these actors, transparency is generally considered to produce desirable e↵ects. For example, transparency can result in a high level of resilience in STSs [3]. However, there are instances where transparency may have adverse e↵ects. For example, in a four-year organisational study, [2] discovered that transparency in the context of a clinical risk management can act, perversely, to undermine ethical behaviour, leading to organisational crisis and even collapse. Consequently, transparency cannot be seen as a one-size-fits-all solution, and when implemented ine↵ectively, it can lead to serious issues in STSs. Transparency may have multiple side-e↵ects on the business goals of actors and their inter-relations. For example, it may lead to information overload or create unnecessary bias and clustering amongst actors. Transparency could be seen either as a special kind of requirement or as a meta-requirement, i.e., to know how a requirement is being fulfilled. In the domain of information systems and requirements engineering, modelling similar social concepts such as trust, privacy and security [5] is motivated by the concept of separation of concerns and modularity. However, despite the importance of transparency, and the unique characteristics and special properties that should be identified with this concept, e.g., deciding the right transparency level and predicting its side-e↵ects, there are no dedicated models, tools or approaches with which to handle transparency. As a result, the fine line that usually exists between balanced transparency, on one side, and the lack or abundance of transparency, on the other, is an under-researched issue. Furthermore, the conflicts that may arise when di↵erent stakeholders need di↵erent levels of transparency are yet to be explored and researched. Example. There are several websites which o↵er audio-to-text transcription services. While users’ actual requirement is the transcription of their audio files to text files, they may also want to know how their requirement is achieved, e.g. whether the transcription is done via an automated process or by handing it over to other people, and if so, how much these people are paid, etc. On the other hand, the policies practised by the transcription service may prevent it from disclosing such information to its users.

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

منابع مشابه

Using i* to Elicit and Model Transparency in the Presence of Other Non-Functional Requirements: A Position Paper

Transparency has been, for long, a general requirement for democratic societies. The right to be informed as well as to have access to information has been an important issue on modern societies. Nowadays, Transparency has been elevated to a must have property to be delivered by governments and businesses. In an era when computer systems are ubiquitous and present in almost every aspect of our ...

متن کامل

Exploring i* Characteristics that Support Software Transparency

This work presents the idea of software transparency. It posits that software transparency must be based on requirements, which will be the baseline for downstream traceability as well as upstream traceability. In that context, i* models are viewed as providing the support for several of the non-functional requirements that impact the software transparency NFR. In particular, we will explore th...

متن کامل

A Modelling Language for Transparency Requirements in Business Information Systems

Transparency is a requirement of businesses and their information systems. It is typically linked to positive ethical and economic attributes, such as trust and accountability. Despite its importance, transparency is often studied as a secondary concept and viewed through the lenses of adjacent concepts such as security, privacy and regulatory requirements. This has led to a reduced ability to ...

متن کامل

Metrics for Transparency

Transparency is a novel non-functional requirement for software systems. It is acclaimed to improve the quality of service since it gives users access to information concerning the system’s processes, clarifying who is responsible if something goes wrong. Thus, it is believed to support people’s right to a secure and private processing of their personal data. We define eight quality metrics for...

متن کامل

Elicitation Awareness in Conceptual Modeling: The Role of Transparency

This talk will review how transparency brings the possibility of process awareness in requirements building. Conceptual modeling has been the prominent facet of requirements engineering with good reasons. The task of specifying, at a high level of abstraction, the myriad of knowledge needed to anchor software development is one of the great challenges of computer science. As such, different art...

متن کامل

ذخیره در منابع من


  با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید

برای دانلود متن کامل این مقاله و بیش از 32 میلیون مقاله دیگر ابتدا ثبت نام کنید

ثبت نام

اگر عضو سایت هستید لطفا وارد حساب کاربری خود شوید

عنوان ژورنال:

دوره   شماره 

صفحات  -

تاریخ انتشار 2015